I tried something with my Garmin 430 yesterday that worked out well so I
thought I would pass it along.

I was doing a series of practice approaches to the area airports that are 10
miles or so apart. The problem was setting up for the next approach while
climbing out from the last. With only a few miles, it was easy to over run the
IAF during setup.

So I put all the airports in a flight plan before takeoff (doesn't matter the
order). Then at any time you can call up the flight plan and with the curser
select any of the airports and do a "direct to". Then select the approach and
you are finished. After the first approach select the flight plan again,
curser to the next airport, "direct to",etc. Sure faster that entering the
next airport identifier one character at a time.

Chuck

Or you can call up the nearest airport list and go direct to one of them,
then you don't have to mess with creating a flight plan.

"PaulaJay1" > wrote in message
...
> I tried something with my Garmin 430 yesterday that worked out well so I
> thought I would pass it along.
>
> I was doing a series of practice approaches to the area airports that are
10
> miles or so apart. The problem was setting up for the next approach while
> climbing out from the last. With only a few miles, it was easy to over
run the
> IAF during setup.
>
> So I put all the airports in a flight plan before takeoff (doesn't matter
the
> order). Then at any time you can call up the flight plan and with the
curser
> select any of the airports and do a "direct to". Then select the approach
and
> you are finished. After the first approach select the flight plan again,
> curser to the next airport, "direct to",etc. Sure faster that entering
the
> next airport identifier one character at a time.
>
> Chuck

You can also stack the approaches into a flight plan if you know the order
your going to fly them.

PaulaJay1 wrote:
> I tried something with my Garmin 430 yesterday that worked out well so I
> thought I would pass it along.
>
> I was doing a series of practice approaches to the area airports that are 10
> miles or so apart. The problem was setting up for the next approach while
> climbing out from the last. With only a few miles, it was easy to over run the
> IAF during setup.
>
> So I put all the airports in a flight plan before takeoff (doesn't matter the
> order). Then at any time you can call up the flight plan and with the curser
> select any of the airports and do a "direct to". Then select the approach and
> you are finished. After the first approach select the flight plan again,
> curser to the next airport, "direct to",etc. Sure faster that entering the
> next airport identifier one character at a time.

On the GX50/GX60, the airport has to be the last element in the flight plan in
order to load an approach for it. Evidently that's not true for the 430.

Dave

In article >, Dave Butler
> writes:

>So I put all the airports in a flight plan before takeoff (doesn't matter the
>> order). Then at any time you can call up the flight plan and with the
>curser
>> select any of the airports and do a "direct to". Then select the approach
>and
>> you are finished. After the first approach select the flight plan again,
>> curser to the next airport, "direct to",etc. Sure faster that entering the
>> next airport identifier one character at a time.
>
>On the GX50/GX60, the airport has to be the last element in the flight plan
>in
>order to load an approach for it. Evidently that's not true for the 430.
>

Same with the 430 if you are flying the flight plan. I am using the flight
plan only to store the identifiers ( which I can load before the takeoff). For
each approach I bring up the flight plan, curser to the airport of choice, and
do a "direct to". The flight plan remains stored to be used for the next
approach by again cursering to the airport of choice, etc.

PaulaJay1 wrote:

>>>you are finished. After the first approach select the flight plan again,
>>>curser to the next airport, "direct to",etc. Sure faster that entering the
>>>next airport identifier one character at a time.
>>
>>On the GX50/GX60, the airport has to be the last element in the flight plan
>>in
>>order to load an approach for it. Evidently that's not true for the 430.
>>
>
>
> Same with the 430 if you are flying the flight plan. I am using the flight
> plan only to store the identifiers ( which I can load before the takeoff). For
> each approach I bring up the flight plan, curser to the airport of choice, and
> do a "direct to". The flight plan remains stored to be used for the next
> approach by again cursering to the airport of choice, etc.

AFAIK in order to do an approach with the GX50/60 you MUST be flying the flight
plan. If you do a DIRECT TO and want to do an approach at the end of the DIRECT
segment, the DIRECT TO must become the flight plan. You specifically can not do
an approach at an airport that's an intermediate waypoint in the active flight
plan. The destination airport for the approach has to be at the end of the
flight plan.

Do you still say "same with the 430"? I have no experience with the 430..

Dave
Remove SHIRT to reply directly.

In article >, Dave Butler
> writes:

>> Same with the 430 if you are flying the flight plan. I am using the flight
>> plan only to store the identifiers ( which I can load before the takeoff).
>For
>> each approach I bring up the flight plan, curser to the airport of choice,
>and
>> do a "direct to". The flight plan remains stored to be used for the next
>> approach by again cursering to the airport of choice, etc.
>
>AFAIK in order to do an approach with the GX50/60 you MUST be flying the
>flight
>plan. If you do a DIRECT TO and want to do an approach at the end of the
>DIRECT
>segment, the DIRECT TO must become the flight plan. You specifically can not
>do
>an approach at an airport that's an intermediate waypoint in the active
>flight
>plan. The destination airport for the approach has to be at the end of the
>flight plan.
>
>Do you still say "same with the 430"? I have no experience with the 430..
>

Well, I checked it out on simulator on my PC. Yes, the approach and hold does
get put at the end of the flight plan even tho you may have selected airport
number 2 out of say a list of 4. However, the list of the 4 airports remains
in the flight plan above the approach and hold. So you can call up the flight
plan and page up to select another airport and then "direct to". Again, the
approach and hold is placed at the end of the flight plan with the first
approach removed and the second one in place.

Chuck